Enduring CSS by Ben Frain

Author:Ben Frain [Ben Frain]
Language: eng
Format: epub, azw3, mobi, pdf
Tags: Web, Programming Languages, Computers, General, Html, Design, Web Development, Web Programming
ISBN: 9781787284531
Google: xU8oDwAAQBAJ
Amazon: B01N5JUQR6
Publisher: Packt Publishing
Published: 2017-01-17T00:00:00+00:00

Tip

When naming the class for the outermost container of a module or component, no child extension should be added to the class/selector. Only the child parts of a module or component should get the node extension.

OK, so, at this point, our selectors could be named like this in the style sheets:

.mod-ShoppingCart {} /*Modal*/ .page-ShoppingCart {} /*Page*/ .mod-ShoppingCartLines {} /*Modal*/ .page-ShoppingCartLines {} /*Page*/

This way our module and component have their two contexts isolated by a namespace switch. We are free to style each as we see fit with no potential leakage of styles from one to the other. This is the exact kind of scenario that typically becomes fraught when components and modules share HTML classes in the interest of abstraction and re-use.

Let's consider a twist on this scenario. Let's suppose we don't switch contexts with application logic. Instead, we have a switch of styles with media queries. We have a modal implementation at smaller viewports and the page style, in normal document flow, at larger viewports.

In this instance, we could have a single namespace e.g. sc-ShoppingCart (I'm using sc- to designate the context is ShoppingCart) and use media queries in the CSS to provide visual changes.

For example:

.sc-ShoppingCart { /*Modal styles for smaller viewports*/ @media (min-width: $M) { /* Page styles for larger viewports */ } } .sc-ShoppingCartLines { /* Modal styles for smaller viewports */ @media (min-width: $M) { /* Page styles for larger viewports */ } }

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.